From: Jan Beulich <jbeulich@suse.com>
Date: Tue, 3 Nov 2015 17:11:15 +0000 (+0100)
Subject: timer-op: demote a debugging message to really be debugging only
X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~2305^2~7
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/success//%22http:/www.example.com/cgi/success/?a=commitdiff_plain;h=e134a69f5c649290accfe2d5e905c5810425b4c4;p=xen.git

timer-op: demote a debugging message to really be debugging only

The issue the message points out may have been of relevance during the
early days, but shouldn't anymore.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
---

diff --git a/xen/common/schedule.c b/xen/common/schedule.c
index c5f640fd73..292e9a07ed 100644
--- a/xen/common/schedule.c
+++ b/xen/common/schedule.c
@@ -1118,8 +1118,8 @@ long do_set_timer_op(s_time_t timeout)
          * timeout in this case can burn a lot of CPU. We therefore go for a
          * reasonable middleground of triggering a timer event in 100ms.
          */
-        gprintk(XENLOG_INFO, "Warning: huge timeout set: %"PRIx64"\n",
-                (uint64_t)timeout);
+        gdprintk(XENLOG_INFO, "Warning: huge timeout set: %"PRIx64"\n",
+                 timeout);
         set_timer(&v->singleshot_timer, NOW() + MILLISECS(100));
     }
     else